Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1c56e96dca58462f0559cbfa4892a439533a6ab292e350ed9c490a4d2f92f6f9

Tx prefix hash: 0590aef6196dd20f359f46f516250faa3a0bed5b25a21e2bed9dca631d5d66d6
Tx public key: d71714c33d2869294223e673f804b88c264109bc7cae5b7d9482fce25b30c3b1
Timestamp: 1702879676 Timestamp [UCT]: 2023-12-18 06:07:56 Age [y:d:h:m:s]: 01:338:11:07:46
Block: 915625 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 500749 RingCT/type: yes/0
Extra: 01d71714c33d2869294223e673f804b88c264109bc7cae5b7d9482fce25b30c3b102110000000775e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2d26435d1a968a5aafaeef79be3798ff5fa3f099a2dbefb02edcdaf359f5f67c 0.600000000000 1373021 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": 915635, "vin": [ { "gen": { "height": 915625 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2d26435d1a968a5aafaeef79be3798ff5fa3f099a2dbefb02edcdaf359f5f67c" } } ], "extra": [ 1, 215, 23, 20, 195, 61, 40, 105, 41, 66, 35, 230, 115, 248, 4, 184, 140, 38, 65, 9, 188, 124, 174, 91, 125, 148, 130, 252, 226, 91, 48, 195, 177, 2, 17, 0, 0, 0, 7, 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