Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ddbab2172366882cefe93a66f34e4f6699e6922cefd3ecedc891018d68b6a07f

Tx prefix hash: a6df17e9ae338ba0aff023348ff11f8aadaf81b8d05c31c9c0a6e7a47832ad58
Tx public key: abd9ee4cc301e1a8ad2fb69d1c93bccd570a31c29571eb9899798ce7d1ade2cf
Timestamp: 1711478543 Timestamp [UCT]: 2024-03-26 18:42:23 Age [y:d:h:m:s]: 01:047:20:25:27
Block: 986933 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 295166 RingCT/type: yes/0
Extra: 01abd9ee4cc301e1a8ad2fb69d1c93bccd570a31c29571eb9899798ce7d1ade2cf02110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 61579b248714a8132df884cbd66e51e3a59d3d10d4301c4abdb2e59b1004df5c 0.600000000000 1447170 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": 986943, "vin": [ { "gen": { "height": 986933 } } ], "vout": [ { "amount": 600000000, "target": { "key": "61579b248714a8132df884cbd66e51e3a59d3d10d4301c4abdb2e59b1004df5c" } } ], "extra": [ 1, 171, 217, 238, 76, 195, 1, 225, 168, 173, 47, 182, 157, 28, 147, 188, 205, 87, 10, 49, 194, 149, 113, 235, 152, 153, 121, 140, 231, 209, 173, 226, 207, 2, 17, 0, 0, 0, 5, 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