Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 320aec3fef04989632959a8b4965efd9d09e784c5b02a27a825cffa26d2d5954

Tx prefix hash: 8f03516a8936f95a9a5059ec6d5d36101ceaa2a3a88afd0a737e0fd795458e6a
Tx public key: 332fad77405fa83e370c4fef3abba130f6c2f427eee94b66a7a662edd82617d3
Timestamp: 1732184226 Timestamp [UCT]: 2024-11-21 10:17:06 Age [y:d:h:m:s]: 00:134:05:45:29
Block: 1158464 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 95771 RingCT/type: yes/0
Extra: 01332fad77405fa83e370c4fef3abba130f6c2f427eee94b66a7a662edd82617d3021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0df0e5c485f9cbd762154e8258c7446a85359dc0e7188399d614daee3f78eb31 0.600000000000 1644093 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": 1158474, "vin": [ { "gen": { "height": 1158464 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0df0e5c485f9cbd762154e8258c7446a85359dc0e7188399d614daee3f78eb31" } } ], "extra": [ 1, 51, 47, 173, 119, 64, 95, 168, 62, 55, 12, 79, 239, 58, 187, 161, 48, 246, 194, 244, 39, 238, 233, 75, 102, 167, 166, 98, 237, 216, 38, 23, 211, 2, 17, 0, 0, 0, 6, 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