Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 38acfc1306982de2a3297f1399b5d10d64ceccf8a3f8c68b7a891b6be9e77f45

Tx prefix hash: 9bc806f0bdefa2c16e2ecec109dd283236b543135e0d21cbac5efd83e91ab967
Tx public key: 47ecbf980dadfd3f11d4d0ef983cd6587f18cc08bf9baa193fc887c03feea3ff
Timestamp: 1711329942 Timestamp [UCT]: 2024-03-25 01:25:42 Age [y:d:h:m:s]: 00:357:09:46:44
Block: 985701 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 255533 RingCT/type: yes/0
Extra: 0147ecbf980dadfd3f11d4d0ef983cd6587f18cc08bf9baa193fc887c03feea3ff0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 63c4c0c9bce16012a6e1ed28f3d685d833c6d62f7695648779345f3d6e5b5a19 0.600000000000 1445918 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": 985711, "vin": [ { "gen": { "height": 985701 } } ], "vout": [ { "amount": 600000000, "target": { "key": "63c4c0c9bce16012a6e1ed28f3d685d833c6d62f7695648779345f3d6e5b5a19" } } ], "extra": [ 1, 71, 236, 191, 152, 13, 173, 253, 63, 17, 212, 208, 239, 152, 60, 214, 88, 127, 24, 204, 8, 191, 155, 170, 25, 63, 200, 135, 192, 63, 238, 163, 255, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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