Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 275f7cfd7dcf194004e0117087ab4083a1cc10878d0d012a3c1e08340606276a

Tx prefix hash: 706d7279a0ce1fa014a2350b10d5865ed224a82c5d2b85efc14013e82c70037b
Tx public key: 27f66ac3c1971f1857b0ab827b41924f61867dce7f073fe3ae2b86a5d0a3d7ca
Timestamp: 1726678556 Timestamp [UCT]: 2024-09-18 16:55:56 Age [y:d:h:m:s]: 00:211:02:26:58
Block: 1112920 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 150696 RingCT/type: yes/0
Extra: 0127f66ac3c1971f1857b0ab827b41924f61867dce7f073fe3ae2b86a5d0a3d7ca021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b656dbabd4ee25d8f4bcf936c8947e75835233d85992957437c68440a3a77c80 0.600000000000 1592411 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": 1112930, "vin": [ { "gen": { "height": 1112920 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b656dbabd4ee25d8f4bcf936c8947e75835233d85992957437c68440a3a77c80" } } ], "extra": [ 1, 39, 246, 106, 195, 193, 151, 31, 24, 87, 176, 171, 130, 123, 65, 146, 79, 97, 134, 125, 206, 127, 7, 63, 227, 174, 43, 134, 165, 208, 163, 215, 202, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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