Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 282fd8bdd24c42a74ee40b4fcffcb70d8085bea992e6142e1f3b2e2c28bae978

Tx prefix hash: c142b1f2241def47c3fb660ff3f157d4fdfbbd6535766e5d12404d25b58db063
Tx public key: 8b1cccd20026b2e49188fd4f85e1d4944988ad22a5040edec3b74bd813072009
Timestamp: 1673410046 Timestamp [UCT]: 2023-01-11 04:07:26 Age [y:d:h:m:s]: 02:301:08:47:13
Block: 672169 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 734775 RingCT/type: yes/0
Extra: 018b1cccd20026b2e49188fd4f85e1d4944988ad22a5040edec3b74bd8130720090211000000018b7b6602000000000000000000

1 output(s) for total of 3.637684474000 dcy

stealth address amount amount idx
00: 7cd6e6a2a34998fd7928465ddbcb5e778b2cce926c043bed523f1b7ed2762a93 3.637684474000 1113686 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": 672179, "vin": [ { "gen": { "height": 672169 } } ], "vout": [ { "amount": 3637684474, "target": { "key": "7cd6e6a2a34998fd7928465ddbcb5e778b2cce926c043bed523f1b7ed2762a93" } } ], "extra": [ 1, 139, 28, 204, 210, 0, 38, 178, 228, 145, 136, 253, 79, 133, 225, 212, 148, 73, 136, 173, 34, 165, 4, 14, 222, 195, 183, 75, 216, 19, 7, 32, 9, 2, 17, 0, 0, 0, 1, 139, 123, 102, 2, 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