Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a041e51c3b9ec6692f013947f9e3382bacd83c572d9a5fd85a1a81787da7fa7f

Tx prefix hash: 72cd51bee60fcf2ae41690b8d64f358a65bf00222fd5f2958c215da7d37a1066
Tx public key: f5728c0a7564c7c2874033f2542312abd5412839f6058da7326ef1a49507ba5f
Timestamp: 1583766815 Timestamp [UCT]: 2020-03-09 15:13:35 Age [y:d:h:m:s]: 04:295:19:47:12
Block: 79530 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1106148 RingCT/type: yes/0
Extra: 01f5728c0a7564c7c2874033f2542312abd5412839f6058da7326ef1a49507ba5f0211000000054ac5aa02000000000000000000

1 output(s) for total of 334.574164371000 dcy

stealth address amount amount idx
00: 4d43101a5b0b485a1f028217d696c2b7ba75202a126649c75d46c748d892631c 334.574164371000 145482 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": 79540, "vin": [ { "gen": { "height": 79530 } } ], "vout": [ { "amount": 334574164371, "target": { "key": "4d43101a5b0b485a1f028217d696c2b7ba75202a126649c75d46c748d892631c" } } ], "extra": [ 1, 245, 114, 140, 10, 117, 100, 199, 194, 135, 64, 51, 242, 84, 35, 18, 171, 213, 65, 40, 57, 246, 5, 141, 167, 50, 110, 241, 164, 149, 7, 186, 95, 2, 17, 0, 0, 0, 5, 74, 197, 170, 2, 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