Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 16572ce06b62cd8fc09e6cf4e6a960e65683229c518bb13a94808a64d6023cf9

Tx prefix hash: 62b8c4da2ef3fcc345656c0262a76931fcb08940d41b7942aec905466cf5565d
Tx public key: 5af27f2c00f3a7b1e2c26aab2a84e27cfe3edea54a3d8db9502fd6bb5cced5e2
Timestamp: 1709530520 Timestamp [UCT]: 2024-03-04 05:35:20 Age [y:d:h:m:s]: 01:105:11:02:55
Block: 970767 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 336302 RingCT/type: yes/0
Extra: 015af27f2c00f3a7b1e2c26aab2a84e27cfe3edea54a3d8db9502fd6bb5cced5e202110000000449a185bb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aeae19d052a79defd51abc7dbe0ac679e283f03ddd36d72be64f86d7a56fd4bc 0.600000000000 1430628 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": 970777, "vin": [ { "gen": { "height": 970767 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aeae19d052a79defd51abc7dbe0ac679e283f03ddd36d72be64f86d7a56fd4bc" } } ], "extra": [ 1, 90, 242, 127, 44, 0, 243, 167, 177, 226, 194, 106, 171, 42, 132, 226, 124, 254, 62, 222, 165, 74, 61, 141, 185, 80, 47, 214, 187, 92, 206, 213, 226, 2, 17, 0, 0, 0, 4, 73, 161, 133, 187, 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