Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f11397f50b4f917d9b80a5da7e5b05fc8af7d557d9d11c32c83172c1ad270327

Tx prefix hash: 71e01b43198b18b8b7fe17a8ffb30911a53751bf76a82b72fb551173edeac8ed
Tx public key: cbb8718feea38c5759c85e7201ae630c797de94d924a0aa2820c1e4ac9706697
Timestamp: 1738032219 Timestamp [UCT]: 2025-01-28 02:43:39 Age [y:d:h:m:s]: 00:141:03:34:42
Block: 1206654 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 100815 RingCT/type: yes/0
Extra: 01cbb8718feea38c5759c85e7201ae630c797de94d924a0aa2820c1e4ac97066970211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 252ff321a77f7760b826af6a13f61565642bdb8f81c59fd84df519af9ccb4546 0.600000000000 1693365 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": 1206664, "vin": [ { "gen": { "height": 1206654 } } ], "vout": [ { "amount": 600000000, "target": { "key": "252ff321a77f7760b826af6a13f61565642bdb8f81c59fd84df519af9ccb4546" } } ], "extra": [ 1, 203, 184, 113, 143, 238, 163, 140, 87, 89, 200, 94, 114, 1, 174, 99, 12, 121, 125, 233, 77, 146, 74, 10, 162, 130, 12, 30, 74, 201, 112, 102, 151, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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