Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8a47ee6f2c090de103646b4bc3d6c2db4d81f6aae0e491050b89bf1997d50ce9

Tx prefix hash: f1eb7a3c4efe95050687f30f75581ffb4afe9a08b7fd2022c8b75e073dba02c5
Tx public key: 0e62cbc7a12b52a892653009469fcc5c3d2c5b25e133abf1d96ab46416374957
Timestamp: 1734467522 Timestamp [UCT]: 2024-12-17 20:32:02 Age [y:d:h:m:s]: 00:325:15:43:29
Block: 1177412 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 230223 RingCT/type: yes/0
Extra: 010e62cbc7a12b52a892653009469fcc5c3d2c5b25e133abf1d96ab464163749570211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 17fc0ca6d1e95e3980a095a4b93c14d5136e3fdab4c80e9c20c130ef8d613c30 0.600000000000 1663783 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": 1177422, "vin": [ { "gen": { "height": 1177412 } } ], "vout": [ { "amount": 600000000, "target": { "key": "17fc0ca6d1e95e3980a095a4b93c14d5136e3fdab4c80e9c20c130ef8d613c30" } } ], "extra": [ 1, 14, 98, 203, 199, 161, 43, 82, 168, 146, 101, 48, 9, 70, 159, 204, 92, 61, 44, 91, 37, 225, 51, 171, 241, 217, 106, 180, 100, 22, 55, 73, 87, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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