Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3e6017b16c5980bba64c62de17e3240584957ccd69f19580829fc258b3f524d4

Tx prefix hash: b5dc6f055d3f11cd0fdf6d7ece016ab2019de1e77795574f0b8f58808b7344fc
Tx public key: dd3be22611878d6b8c4f58601a5c9fb89d08e3717ac93b790c477ac27f24198d
Timestamp: 1708759813 Timestamp [UCT]: 2024-02-24 07:30:13 Age [y:d:h:m:s]: 01:054:09:56:20
Block: 964368 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 299923 RingCT/type: yes/0
Extra: 01dd3be22611878d6b8c4f58601a5c9fb89d08e3717ac93b790c477ac27f24198d02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6f1514a0180a615168aa1a8e37e2dea526a5c7e445163913c73cb6610e2f4748 0.600000000000 1424099 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": 964378, "vin": [ { "gen": { "height": 964368 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6f1514a0180a615168aa1a8e37e2dea526a5c7e445163913c73cb6610e2f4748" } } ], "extra": [ 1, 221, 59, 226, 38, 17, 135, 141, 107, 140, 79, 88, 96, 26, 92, 159, 184, 157, 8, 227, 113, 122, 201, 59, 121, 12, 71, 122, 194, 127, 36, 25, 141, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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