Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3548aff91829aed4c60fbd73d3715137c67b4d4d884407067eb36dadf441e754

Tx prefix hash: a982399a445c4ca2ceab9c233f1d95a24c8ad4e69567e7b3bf7a899424f526f5
Tx public key: 85410f9f54046ae9efa88a958fec2c2aa80c1f91be93f643666368c83614078a
Timestamp: 1678682174 Timestamp [UCT]: 2023-03-13 04:36:14 Age [y:d:h:m:s]: 01:306:00:39:31
Block: 715905 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 479616 RingCT/type: yes/0
Extra: 0185410f9f54046ae9efa88a958fec2c2aa80c1f91be93f643666368c83614078a021100000001faf35c9c000000000000000000

1 output(s) for total of 2.605650158000 dcy

stealth address amount amount idx
00: 17984225ba171cc434bfd95ec80fd3fb0b1f0087e133cb806e568ad4a26e70e8 2.605650158000 1160224 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": 715915, "vin": [ { "gen": { "height": 715905 } } ], "vout": [ { "amount": 2605650158, "target": { "key": "17984225ba171cc434bfd95ec80fd3fb0b1f0087e133cb806e568ad4a26e70e8" } } ], "extra": [ 1, 133, 65, 15, 159, 84, 4, 106, 233, 239, 168, 138, 149, 143, 236, 44, 42, 168, 12, 31, 145, 190, 147, 246, 67, 102, 99, 104, 200, 54, 20, 7, 138, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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