Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4524adb9cd080ff287707b8a80ac4e12b208eff089e05c8f27002ee578f12573

Tx prefix hash: fb2071da16a6936d0aabc6b5e973bc1e68a5dbe0489b834534ef6e4622029d7a
Tx public key: 9c1af8842bffff3a7230b304cebd9f8ce98dddc1e6ee71731529d63af469db8a
Timestamp: 1730989781 Timestamp [UCT]: 2024-11-07 14:29:41 Age [y:d:h:m:s]: 00:149:19:46:46
Block: 1148581 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106911 RingCT/type: yes/0
Extra: 019c1af8842bffff3a7230b304cebd9f8ce98dddc1e6ee71731529d63af469db8a0211000000048368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d8c2c7588f8e974aa3d0ce7e2906b3d4d20ae74451113efd513bf9ec72c8e5d8 0.600000000000 1633462 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": 1148591, "vin": [ { "gen": { "height": 1148581 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d8c2c7588f8e974aa3d0ce7e2906b3d4d20ae74451113efd513bf9ec72c8e5d8" } } ], "extra": [ 1, 156, 26, 248, 132, 43, 255, 255, 58, 114, 48, 179, 4, 206, 189, 159, 140, 233, 141, 221, 193, 230, 238, 113, 115, 21, 41, 214, 58, 244, 105, 219, 138, 2, 17, 0, 0, 0, 4, 131, 104, 38, 109, 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