Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9ef0d1c383d60806b58b6df5be2acf9a03d3c32c963b28aef53cbf7e72cf74cc

Tx prefix hash: 120ad7212c53ecd2162f5572d877a867a8e04a90573edff1cb11a6942b8ac62a
Tx public key: 36a7930dd25def9fd10a01e82ce95b5e41235eef325be2c240bb3efa98c60f52
Timestamp: 1706369260 Timestamp [UCT]: 2024-01-27 15:27:40 Age [y:d:h:m:s]: 01:144:04:56:08
Block: 944527 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 364056 RingCT/type: yes/0
Extra: 0136a7930dd25def9fd10a01e82ce95b5e41235eef325be2c240bb3efa98c60f5202110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 11f7a86abf943dbc18c3ba32ed9f966f76d5fce535becbece47e5fbf3fd87e09 0.600000000000 1402795 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": 944537, "vin": [ { "gen": { "height": 944527 } } ], "vout": [ { "amount": 600000000, "target": { "key": "11f7a86abf943dbc18c3ba32ed9f966f76d5fce535becbece47e5fbf3fd87e09" } } ], "extra": [ 1, 54, 167, 147, 13, 210, 93, 239, 159, 209, 10, 1, 232, 44, 233, 91, 94, 65, 35, 94, 239, 50, 91, 226, 194, 64, 187, 62, 250, 152, 198, 15, 82, 2, 17, 0, 0, 0, 5, 82, 212, 126, 148, 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