Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b15309200de5d68eaf19fabb0b09257a943b3b86eeacaa41337bdb730998dd34

Tx prefix hash: 4b9da5072e1d1f326f93354fdbc475caedd1bec91bdfa1aa87cfcb83eb8f4cc5
Tx public key: e58d3ddb4565c46ebb2d4e593fdf0b0889fb617e8671dad4b98c8c79f5cbd667
Timestamp: 1672170323 Timestamp [UCT]: 2022-12-27 19:45:23 Age [y:d:h:m:s]: 02:317:22:00:36
Block: 661895 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 746630 RingCT/type: yes/0
Extra: 01e58d3ddb4565c46ebb2d4e593fdf0b0889fb617e8671dad4b98c8c79f5cbd66702110000000afaf35c9c000000000000000000

1 output(s) for total of 3.934296336000 dcy

stealth address amount amount idx
00: 942ee9d16cca7636502aa9017d7ffe52f9d75e8b6ad94d5d25fbf7d14128b2d9 3.934296336000 1102714 of 0

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": 661905, "vin": [ { "gen": { "height": 661895 } } ], "vout": [ { "amount": 3934296336, "target": { "key": "942ee9d16cca7636502aa9017d7ffe52f9d75e8b6ad94d5d25fbf7d14128b2d9" } } ], "extra": [ 1, 229, 141, 61, 219, 69, 101, 196, 110, 187, 45, 78, 89, 63, 223, 11, 8, 137, 251, 97, 126, 134, 113, 218, 212, 185, 140, 140, 121, 245, 203, 214, 103, 2, 17, 0, 0, 0, 10, 250, 243, 92, 156, 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