Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb15518cb6431e26fd9e4c80ade1557075568c7fdfd90d15755c6363d8b49789

Tx prefix hash: a6b44823de663dadac2d4857cddfaf5627930217d2c9f44764f0e707b16d97bc
Tx public key: 93e1731e0f71d84526dc597845bbabf70f2aadb24dda15a4c37b47782763cf9f
Timestamp: 1578549678 Timestamp [UCT]: 2020-01-09 06:01:18 Age [y:d:h:m:s]: 05:025:21:50:59
Block: 41802 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1168432 RingCT/type: yes/0
Extra: 0193e1731e0f71d84526dc597845bbabf70f2aadb24dda15a4c37b47782763cf9f02110000000ebd0f9f9f000000000000000000

1 output(s) for total of 446.172592131000 dcy

stealth address amount amount idx
00: 0c4c57deeb288ce50a9919a8ce7355157d19ca6a6f42a01b5c7d2013d6860a3b 446.172592131000 74868 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": 41812, "vin": [ { "gen": { "height": 41802 } } ], "vout": [ { "amount": 446172592131, "target": { "key": "0c4c57deeb288ce50a9919a8ce7355157d19ca6a6f42a01b5c7d2013d6860a3b" } } ], "extra": [ 1, 147, 225, 115, 30, 15, 113, 216, 69, 38, 220, 89, 120, 69, 187, 171, 247, 15, 42, 173, 178, 77, 218, 21, 164, 195, 123, 71, 120, 39, 99, 207, 159, 2, 17, 0, 0, 0, 14, 189, 15, 159, 159, 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