Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a983ef076e257b590ac208fd2ab67a0af6144e8095cbe818c06713448d3c6950

Tx prefix hash: 61ba13bdfef94a7f5b78e2e82a63264075ebb2fe6e9498afc5200e454432a859
Tx public key: e9cb39456dd0faf7b897cc9267c290bb92e7a54ae7e711ab35b8f66dba207d42
Timestamp: 1580788031 Timestamp [UCT]: 2020-02-04 03:47:11 Age [y:d:h:m:s]: 05:275:05:34:15
Block: 58177 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1346521 RingCT/type: yes/0
Extra: 01e9cb39456dd0faf7b897cc9267c290bb92e7a54ae7e711ab35b8f66dba207d42021100000003dcee4b4d000000000000000000

1 output(s) for total of 393.775347073000 dcy

stealth address amount amount idx
00: 8c69d14e4ba35f09f302c5c69df16e4d898215dcf14d8a8d67f2d8ca5269e5b3 393.775347073000 107545 of 0

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": 58187, "vin": [ { "gen": { "height": 58177 } } ], "vout": [ { "amount": 393775347073, "target": { "key": "8c69d14e4ba35f09f302c5c69df16e4d898215dcf14d8a8d67f2d8ca5269e5b3" } } ], "extra": [ 1, 233, 203, 57, 69, 109, 208, 250, 247, 184, 151, 204, 146, 103, 194, 144, 187, 146, 231, 165, 74, 231, 231, 17, 171, 53, 184, 246, 109, 186, 32, 125, 66, 2, 17, 0, 0, 0, 3, 220, 238, 75, 77, 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