Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 059cb8596cc5c78e89e297d24770e6b8d919a9795033ccbd8eaa98da11a026dc

Tx prefix hash: 31015fd9916696ae2b2d7fe5d21b6e6ddd77e10e7b77eed5e59f2c4af278ecce
Tx public key: 8c37e0705759a0c2171456c42dc49df636a74e27575f670441391712e8ca80d4
Timestamp: 1712509553 Timestamp [UCT]: 2024-04-07 17:05:53 Age [y:d:h:m:s]: 01:040:15:14:27
Block: 995421 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 290061 RingCT/type: yes/0
Extra: 018c37e0705759a0c2171456c42dc49df636a74e27575f670441391712e8ca80d40211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c125aa663a2cf3a004ab1fda1a3b793bc6f3b12f085c03f2111e5077d2337866 0.600000000000 1455829 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": 995431, "vin": [ { "gen": { "height": 995421 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c125aa663a2cf3a004ab1fda1a3b793bc6f3b12f085c03f2111e5077d2337866" } } ], "extra": [ 1, 140, 55, 224, 112, 87, 89, 160, 194, 23, 20, 86, 196, 45, 196, 157, 246, 54, 167, 78, 39, 87, 95, 103, 4, 65, 57, 23, 18, 232, 202, 128, 212, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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