Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 096a50966c243ed86e6e91cd0b03135f4e716120f5a71233ec903335e3058789

Tx prefix hash: a24e8b11cd8c14673c8f79c0ced5255f7ba9c1edac6fbb411c5ad31ab00c5aac
Tx public key: 5821ee80f8e503a4c97e4791e7a6c0b9c92f52a385921c6f46de5a0bc0468950
Timestamp: 1724725632 Timestamp [UCT]: 2024-08-27 02:27:12 Age [y:d:h:m:s]: 00:226:20:41:12
Block: 1096719 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 162012 RingCT/type: yes/0
Extra: 015821ee80f8e503a4c97e4791e7a6c0b9c92f52a385921c6f46de5a0bc0468950021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fce8f1fe58218b163a523b6e8838f2f16a629bcf6fb32ae9e875a79ef4eef2f8 0.600000000000 1571914 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": 1096729, "vin": [ { "gen": { "height": 1096719 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fce8f1fe58218b163a523b6e8838f2f16a629bcf6fb32ae9e875a79ef4eef2f8" } } ], "extra": [ 1, 88, 33, 238, 128, 248, 229, 3, 164, 201, 126, 71, 145, 231, 166, 192, 185, 201, 47, 82, 163, 133, 146, 28, 111, 70, 222, 90, 11, 192, 70, 137, 80, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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