Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 32cb3281dc751bc1c7bce11f1b0901e0d39e7566516a17cf52a7973a077c25c3

Tx prefix hash: 0d5551eedc4be7051563e72628238a87a65775e3a79deb2fbf75e341c1c3f3b4
Tx public key: 86562ce0a2c8ef06210aba516ef2ae86527cbf228cbe0366de0da2bfd5f6b984
Timestamp: 1681401039 Timestamp [UCT]: 2023-04-13 15:50:39 Age [y:d:h:m:s]: 02:042:08:20:40
Block: 737783 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 552464 RingCT/type: yes/0
Extra: 0186562ce0a2c8ef06210aba516ef2ae86527cbf228cbe0366de0da2bfd5f6b98402110000000175e3f0e9000000000000000000

1 output(s) for total of 2.205052194000 dcy

stealth address amount amount idx
00: 7f5486c3113a60ff510f9de1ea67a358936644997d6e956ae5754dbccc856954 2.205052194000 1184384 of 0

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": 737793, "vin": [ { "gen": { "height": 737783 } } ], "vout": [ { "amount": 2205052194, "target": { "key": "7f5486c3113a60ff510f9de1ea67a358936644997d6e956ae5754dbccc856954" } } ], "extra": [ 1, 134, 86, 44, 224, 162, 200, 239, 6, 33, 10, 186, 81, 110, 242, 174, 134, 82, 124, 191, 34, 140, 190, 3, 102, 222, 13, 162, 191, 213, 246, 185, 132, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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