Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 87bcf22f0c58aa278da80fe947ec1b0aa12a4d4eac7e2c66163d451a13742065

Tx prefix hash: 2d19472129da0d63e10b22085cf8fa823bb17481664afa9c9f8a212d337ff2f0
Tx public key: e080f4a1087a41bcdd6891e50e0199d33ad64ce3f0991cd0276fd4f65a11d4ed
Timestamp: 1724133557 Timestamp [UCT]: 2024-08-20 05:59:17 Age [y:d:h:m:s]: 00:232:21:35:17
Block: 1091829 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 166323 RingCT/type: yes/0
Extra: 01e080f4a1087a41bcdd6891e50e0199d33ad64ce3f0991cd0276fd4f65a11d4ed02110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 33ea9d4359dd0bb5a0290d3ec9477314e5f7553087a661024eea6efcb97b90d5 0.600000000000 1566464 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": 1091839, "vin": [ { "gen": { "height": 1091829 } } ], "vout": [ { "amount": 600000000, "target": { "key": "33ea9d4359dd0bb5a0290d3ec9477314e5f7553087a661024eea6efcb97b90d5" } } ], "extra": [ 1, 224, 128, 244, 161, 8, 122, 65, 188, 221, 104, 145, 229, 14, 1, 153, 211, 58, 214, 76, 227, 240, 153, 28, 208, 39, 111, 212, 246, 90, 17, 212, 237, 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