Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0387d3d1c93d5f06c487fb9cbc2c0aadd0973928c90fdcbfb0733ef93951789f

Tx prefix hash: 1d054701e4822c1665223a94d62a3088f83a173d099775b9614d8ccdbefbb38b
Tx public key: 0112e6f66849ae4e21e9925bf0fbb5a1dc80b5b666140d68a4254497caa293b6
Timestamp: 1710135475 Timestamp [UCT]: 2024-03-11 05:37:55 Age [y:d:h:m:s]: 01:064:12:00:04
Block: 975780 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 307121 RingCT/type: yes/0
Extra: 010112e6f66849ae4e21e9925bf0fbb5a1dc80b5b666140d68a4254497caa293b602110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d22989466d646e79216e71b45e9cdb444a7d389306c9da9fa454d7cb65874bf5 0.600000000000 1435755 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": 975790, "vin": [ { "gen": { "height": 975780 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d22989466d646e79216e71b45e9cdb444a7d389306c9da9fa454d7cb65874bf5" } } ], "extra": [ 1, 1, 18, 230, 246, 104, 73, 174, 78, 33, 233, 146, 91, 240, 251, 181, 161, 220, 128, 181, 182, 102, 20, 13, 104, 164, 37, 68, 151, 202, 162, 147, 182, 2, 17, 0, 0, 0, 1, 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