Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8612f50028716d22372c662f0894a01b5e9b3c60ea1ce773b62a5c0ad26159f8

Tx prefix hash: ad17469d220b5c8ad3a28c1e2935691802bbd99e42d2f11e5c11e5c28bd5bb78
Tx public key: f2109286127171f1a680dd3dce6976a33aed3cc2b087713570e2f539d449e054
Timestamp: 1731406701 Timestamp [UCT]: 2024-11-12 10:18:21 Age [y:d:h:m:s]: 00:139:11:42:25
Block: 1152030 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 99521 RingCT/type: yes/0
Extra: 01f2109286127171f1a680dd3dce6976a33aed3cc2b087713570e2f539d449e054021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 69ecdffaf150bb4d4da8e0ddfb1f669fdc853d73da56b7ab1a20b4b0ad8d11b8 0.600000000000 1637621 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": 1152040, "vin": [ { "gen": { "height": 1152030 } } ], "vout": [ { "amount": 600000000, "target": { "key": "69ecdffaf150bb4d4da8e0ddfb1f669fdc853d73da56b7ab1a20b4b0ad8d11b8" } } ], "extra": [ 1, 242, 16, 146, 134, 18, 113, 113, 241, 166, 128, 221, 61, 206, 105, 118, 163, 58, 237, 60, 194, 176, 135, 113, 53, 112, 226, 245, 57, 212, 73, 224, 84, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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