Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ab6ca328e56a55c113c1711e501aa404a626462f5cbcdb658aeac35947a2c161

Tx prefix hash: 16c28fec5f2fa1a809e3f4df4bfc0f28313c2997a431e4ab29d793ef0c3109da
Tx public key: f4c7eda43670b9d21aef7d21c11a2e3e2468b1c991dd1a4a02edef362ac6c359
Timestamp: 1731527039 Timestamp [UCT]: 2024-11-13 19:43:59 Age [y:d:h:m:s]: 00:135:10:26:53
Block: 1153033 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 96611 RingCT/type: yes/0
Extra: 01f4c7eda43670b9d21aef7d21c11a2e3e2468b1c991dd1a4a02edef362ac6c359021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7b971d6020fa5055f7dbd82a2480bbee28475d3c0fcb8e6a053b0d00d700e5ac 0.600000000000 1638640 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": 1153043, "vin": [ { "gen": { "height": 1153033 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7b971d6020fa5055f7dbd82a2480bbee28475d3c0fcb8e6a053b0d00d700e5ac" } } ], "extra": [ 1, 244, 199, 237, 164, 54, 112, 185, 210, 26, 239, 125, 33, 193, 26, 46, 62, 36, 104, 177, 201, 145, 221, 26, 74, 2, 237, 239, 54, 42, 198, 195, 89, 2, 17, 0, 0, 0, 3, 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