Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c8a867528af081e9b07e9d81eb145192a770608227cf1639e994b11f560802fb

Tx prefix hash: af2ff013012b03cc08308a0a3340d0110b8a0ed429635fe25fa240d9737f591c
Tx public key: 3a28abcb406de6a894b5d5008f1569ee77d1736b0ce11785637cbee3b9f8b9b1
Timestamp: 1731107646 Timestamp [UCT]: 2024-11-08 23:14:06 Age [y:d:h:m:s]: 00:133:19:57:54
Block: 1149561 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 95471 RingCT/type: yes/0
Extra: 013a28abcb406de6a894b5d5008f1569ee77d1736b0ce11785637cbee3b9f8b9b1021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7ee0d57967bef8fc7ff1d4251d93cf02791f8fd0b268397decfbfe834472857c 0.600000000000 1634664 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": 1149571, "vin": [ { "gen": { "height": 1149561 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7ee0d57967bef8fc7ff1d4251d93cf02791f8fd0b268397decfbfe834472857c" } } ], "extra": [ 1, 58, 40, 171, 203, 64, 109, 230, 168, 148, 181, 213, 0, 143, 21, 105, 238, 119, 209, 115, 107, 12, 225, 23, 133, 99, 124, 190, 227, 185, 248, 185, 177, 2, 17, 0, 0, 0, 1, 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