Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8193f873366ba2a0f336c3f37c76e3ed77251ac9d3337e6818dc384d0ef7577b

Tx prefix hash: 59b7bc03b21205b79b261a70b33361b0e0bef7659e4e659d55254171d3ee5be0
Tx public key: 376fc26d12d66ada62c6e5b9aae73fd65566f3a1caba1652bd48e9e787e15edd
Timestamp: 1720410162 Timestamp [UCT]: 2024-07-08 03:42:42 Age [y:d:h:m:s]: 00:266:16:03:13
Block: 1060956 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 190524 RingCT/type: yes/0
Extra: 01376fc26d12d66ada62c6e5b9aae73fd65566f3a1caba1652bd48e9e787e15edd02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 39ef4f2ea809e2a9d1ca672aafc5799ca1475cc2ed60696700687bf0f7e65a58 0.600000000000 1531445 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": 1060966, "vin": [ { "gen": { "height": 1060956 } } ], "vout": [ { "amount": 600000000, "target": { "key": "39ef4f2ea809e2a9d1ca672aafc5799ca1475cc2ed60696700687bf0f7e65a58" } } ], "extra": [ 1, 55, 111, 194, 109, 18, 214, 106, 218, 98, 198, 229, 185, 170, 231, 63, 214, 85, 102, 243, 161, 202, 186, 22, 82, 189, 72, 233, 231, 135, 225, 94, 221, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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