Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a89b14da9588a75e7d2f8dde4b38364fd2c8ec5ad346cd8462d7338a4c58f9a3

Tx prefix hash: be75c5182f7d9628511acc11e9a4db35b0cc3164f2797dd7513f2aafcf3bde15
Tx public key: 92428d48d3c8aa6d91e5dc95e6bcdf1fe06923088caba5c30aa5f4a1836f4649
Timestamp: 1722966082 Timestamp [UCT]: 2024-08-06 17:41:22 Age [y:d:h:m:s]: 00:246:21:01:30
Block: 1082142 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 176341 RingCT/type: yes/0
Extra: 0192428d48d3c8aa6d91e5dc95e6bcdf1fe06923088caba5c30aa5f4a1836f4649021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 72e66c8cc3d66602414b7652abdcb7d702fd35042c7c499f0ae310c2cf7dcfaf 0.600000000000 1555965 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": 1082152, "vin": [ { "gen": { "height": 1082142 } } ], "vout": [ { "amount": 600000000, "target": { "key": "72e66c8cc3d66602414b7652abdcb7d702fd35042c7c499f0ae310c2cf7dcfaf" } } ], "extra": [ 1, 146, 66, 141, 72, 211, 200, 170, 109, 145, 229, 220, 149, 230, 188, 223, 31, 224, 105, 35, 8, 140, 171, 165, 195, 10, 165, 244, 161, 131, 111, 70, 73, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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