Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b19f310e337cf1f45b2fdc7641b8951799fa54a3a98672bdb9881863ada1dae8

Tx prefix hash: bb06f2099ed236cf1aed95e6e31cf6c3a68c655f4242de86dc5309f5125259fd
Tx public key: 52908be2f1f7bba786cf65d7e9dc70809927a559e3db34bca3be1d7998c4817a
Timestamp: 1742184925 Timestamp [UCT]: 2025-03-17 04:15:25 Age [y:d:h:m:s]: 00:319:04:49:00
Block: 1241016 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 225788 RingCT/type: yes/0
Extra: 0152908be2f1f7bba786cf65d7e9dc70809927a559e3db34bca3be1d7998c4817a02110000000c007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4fb1a883681b45c15bea21942b1be43dd9d275a0cfb35567b995858df60d1374 0.600000000000 1727989 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": 1241026, "vin": [ { "gen": { "height": 1241016 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4fb1a883681b45c15bea21942b1be43dd9d275a0cfb35567b995858df60d1374" } } ], "extra": [ 1, 82, 144, 139, 226, 241, 247, 187, 167, 134, 207, 101, 215, 233, 220, 112, 128, 153, 39, 165, 89, 227, 219, 52, 188, 163, 190, 29, 121, 152, 196, 129, 122, 2, 17, 0, 0, 0, 12, 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