Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 74ed2c47b3dde357159acbcf2b1dc48ac3f4fc624266af2c030769cff7ab4146

Tx prefix hash: c39c08328fc00babe30aba98fb6bc24185093bddc215cef1dd0e9c6fd0991ddc
Tx public key: c184e4c724071b57a7bcf840afd9ff86cbc7d8979d3fb270f8d06dd81a8e1890
Timestamp: 1737048642 Timestamp [UCT]: 2025-01-16 17:30:42 Age [y:d:h:m:s]: 00:156:09:22:48
Block: 1198750 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111406 RingCT/type: yes/0
Extra: 01c184e4c724071b57a7bcf840afd9ff86cbc7d8979d3fb270f8d06dd81a8e1890021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e2d9367331ea29ff4c2eaf66d4aa08dd367084f59b87a89698bd26e962642d54 0.600000000000 1685377 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": 1198760, "vin": [ { "gen": { "height": 1198750 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e2d9367331ea29ff4c2eaf66d4aa08dd367084f59b87a89698bd26e962642d54" } } ], "extra": [ 1, 193, 132, 228, 199, 36, 7, 27, 87, 167, 188, 248, 64, 175, 217, 255, 134, 203, 199, 216, 151, 157, 63, 178, 112, 248, 208, 109, 216, 26, 142, 24, 144, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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