Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8b992fff9758c1b34e1a3c37f33e024295a41c5d60f80105e827b6d6fd529576

Tx prefix hash: d39f4ba3d83aa3fce5f14501a4e31336464568517e538f08b82723fd48539a88
Tx public key: 1b265106a632240e97ddcd651769bc0c65f695392dbf74b1f30ea3b3cf273559
Timestamp: 1705468242 Timestamp [UCT]: 2024-01-17 05:10:42 Age [y:d:h:m:s]: 01:096:13:48:11
Block: 937048 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 330141 RingCT/type: yes/0
Extra: 011b265106a632240e97ddcd651769bc0c65f695392dbf74b1f30ea3b3cf2735590211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f4ef87d3b1d97a856dd5081fe88dc35c6f7ab9858e034021d0f919dd6af021ae 0.600000000000 1395092 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": 937058, "vin": [ { "gen": { "height": 937048 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f4ef87d3b1d97a856dd5081fe88dc35c6f7ab9858e034021d0f919dd6af021ae" } } ], "extra": [ 1, 27, 38, 81, 6, 166, 50, 36, 14, 151, 221, 205, 101, 23, 105, 188, 12, 101, 246, 149, 57, 45, 191, 116, 177, 243, 14, 163, 179, 207, 39, 53, 89, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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