Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 399e3f895bbfe11bc9ec315a830b82642d7ee944d4569c56336e293da1d7644f

Tx prefix hash: 64a2dcc7d44c27d383dc2b26a9c7cbe14b4c7671097dbbefecfb3684cbc88fe8
Tx public key: a97ec84cfb908f06eecb1c2f53a9a61a90f241c8bc14680fd8d55cb121fda045
Timestamp: 1711464510 Timestamp [UCT]: 2024-03-26 14:48:30 Age [y:d:h:m:s]: 00:212:23:38:07
Block: 986816 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 152497 RingCT/type: yes/0
Extra: 01a97ec84cfb908f06eecb1c2f53a9a61a90f241c8bc14680fd8d55cb121fda04502110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0c5add6e1f8232624cb2b95bd5cc6ab7fb51c5df50663172f643c0c484090b4b 0.600000000000 1447051 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": 986826, "vin": [ { "gen": { "height": 986816 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0c5add6e1f8232624cb2b95bd5cc6ab7fb51c5df50663172f643c0c484090b4b" } } ], "extra": [ 1, 169, 126, 200, 76, 251, 144, 143, 6, 238, 203, 28, 47, 83, 169, 166, 26, 144, 242, 65, 200, 188, 20, 104, 15, 216, 213, 92, 177, 33, 253, 160, 69, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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