Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 60e5a6f9b7b998e0f7bce01291b2af85a748f7fb9b7ce68dfea6dfeb896ea464

Tx prefix hash: 22a05d2354d0901c6cf3bb12758acfb3b612a34c6dec34eb8f6fc86b95931641
Tx public key: c8c994086bb445fcce8cf993177f2c29d3ea71c60c6175e6960b1af877a727cd
Timestamp: 1721278287 Timestamp [UCT]: 2024-07-18 04:51:27 Age [y:d:h:m:s]: 00:133:03:40:48
Block: 1068169 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 95261 RingCT/type: yes/0
Extra: 01c8c994086bb445fcce8cf993177f2c29d3ea71c60c6175e6960b1af877a727cd02110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9e5f2e37303355059d2f73b566e0e24e86cbaa2d2bcb97a962cae3f6b54e83fe 0.600000000000 1539214 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": 1068179, "vin": [ { "gen": { "height": 1068169 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9e5f2e37303355059d2f73b566e0e24e86cbaa2d2bcb97a962cae3f6b54e83fe" } } ], "extra": [ 1, 200, 201, 148, 8, 107, 180, 69, 252, 206, 140, 249, 147, 23, 127, 44, 41, 211, 234, 113, 198, 12, 97, 117, 230, 150, 11, 26, 248, 119, 167, 39, 205, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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