Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b18c8d6f8ab40437f97457bc9c70eb7a5223960b48141e5bdc55ae1649e8526d

Tx prefix hash: f528cc783173666c1ee9a17fd43451e0c9649fae84ada269687a7fedccb2e4ff
Tx public key: 0a9168858c9017e8ed0ef75776c9891dac30c43f1e77bf8fba3cdf25eaf1a2aa
Timestamp: 1732346339 Timestamp [UCT]: 2024-11-23 07:18:59 Age [y:d:h:m:s]: 00:349:21:42:43
Block: 1159822 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 247605 RingCT/type: yes/0
Extra: 010a9168858c9017e8ed0ef75776c9891dac30c43f1e77bf8fba3cdf25eaf1a2aa021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6051afd5b922c4476a88e95bfbca0d5e316b15168334cec5fdf4bb76f0d79924 0.600000000000 1645461 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": 1159832, "vin": [ { "gen": { "height": 1159822 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6051afd5b922c4476a88e95bfbca0d5e316b15168334cec5fdf4bb76f0d79924" } } ], "extra": [ 1, 10, 145, 104, 133, 140, 144, 23, 232, 237, 14, 247, 87, 118, 201, 137, 29, 172, 48, 196, 63, 30, 119, 191, 143, 186, 60, 223, 37, 234, 241, 162, 170, 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