Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 819fb8d276528f6c5c3d597c1a173ae61af0554d148150159012a6f38c2dd533

Tx prefix hash: 0feab882ab52191df773999565f670e8e4ca7989616f72f5381292a12a7ca96a
Tx public key: 23a66ab76838d850c965f71d40f5c9c31f8d4f949f215af9a6b0c0d2c969d3d0
Timestamp: 1737487383 Timestamp [UCT]: 2025-01-21 19:23:03 Age [y:d:h:m:s]: 00:147:12:15:33
Block: 1202338 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105168 RingCT/type: yes/0
Extra: 0123a66ab76838d850c965f71d40f5c9c31f8d4f949f215af9a6b0c0d2c969d3d0021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bf5a2882aac29d577e74f77027497ab37b447eb52431d9ea4c81fbc3fa3948ba 0.600000000000 1689001 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1202348, "vin": [ { "gen": { "height": 1202338 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bf5a2882aac29d577e74f77027497ab37b447eb52431d9ea4c81fbc3fa3948ba" } } ], "extra": [ 1, 35, 166, 106, 183, 104, 56, 216, 80, 201, 101, 247, 29, 64, 245, 201, 195, 31, 141, 79, 148, 159, 33, 90, 249, 166, 176, 192, 210, 201, 105, 211, 208, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8