Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f8acf6f5bda72b4e8eab9383365fe6ba731eac2c45a47a02f7c42e4c01b2b879

Tx prefix hash: 39278785f0d645d1653875bde506f0227f250aa083d8ce2cc8a83270b746ccb6
Tx public key: 0e35760b2e2ce87602fc2f2e967b32757bb9d8dc2bceff1939a8b3a91dec5175
Timestamp: 1724827193 Timestamp [UCT]: 2024-08-28 06:39:53 Age [y:d:h:m:s]: 00:228:09:15:56
Block: 1097573 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 163101 RingCT/type: yes/0
Extra: 010e35760b2e2ce87602fc2f2e967b32757bb9d8dc2bceff1939a8b3a91dec517502110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d58f3139b04756d2ce2e84f9887bbfd516eede4d40962e8067bd09536777ea37 0.600000000000 1572980 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": 1097583, "vin": [ { "gen": { "height": 1097573 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d58f3139b04756d2ce2e84f9887bbfd516eede4d40962e8067bd09536777ea37" } } ], "extra": [ 1, 14, 53, 118, 11, 46, 44, 232, 118, 2, 252, 47, 46, 150, 123, 50, 117, 123, 185, 216, 220, 43, 206, 255, 25, 57, 168, 179, 169, 29, 236, 81, 117, 2, 17, 0, 0, 0, 3, 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