Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b2b73e75e397a5fa7904e2a14de4cbedb2ec967182113e803285890b4e797eac

Tx prefix hash: 9ea480aa450b1183a22d20a27c575e6ac6a927c04bf1ebcffbf2e7eb8838917a
Tx public key: d22009dcecc4900eb272cfb9148ccfb23e37bd2bff038b6ebf06345583a8d4ee
Timestamp: 1721295491 Timestamp [UCT]: 2024-07-18 09:38:11 Age [y:d:h:m:s]: 00:259:16:11:21
Block: 1068311 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 185484 RingCT/type: yes/0
Extra: 01d22009dcecc4900eb272cfb9148ccfb23e37bd2bff038b6ebf06345583a8d4ee02110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 12782fce26d12449e7ef9d09d8e57c5c7ed1d1d39bf1a34c20f93b8e25414182 0.600000000000 1539388 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": 1068321, "vin": [ { "gen": { "height": 1068311 } } ], "vout": [ { "amount": 600000000, "target": { "key": "12782fce26d12449e7ef9d09d8e57c5c7ed1d1d39bf1a34c20f93b8e25414182" } } ], "extra": [ 1, 210, 32, 9, 220, 236, 196, 144, 14, 178, 114, 207, 185, 20, 140, 207, 178, 62, 55, 189, 43, 255, 3, 139, 110, 191, 6, 52, 85, 131, 168, 212, 238, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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