Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 31f91318ca190cde20fdc5f391a857413328d81074afd62ad840e4b088582fc4

Tx prefix hash: 4cd9b96d7910f9e9003cb9e8763f35156d424903686d5af225691a344ff13b29
Tx public key: 66fd1ab355319b092d71c081cdbfef8782794eaf96513289626aad741d3b48f0
Timestamp: 1579177525 Timestamp [UCT]: 2020-01-16 12:25:25 Age [y:d:h:m:s]: 05:049:00:09:43
Block: 46814 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1185141 RingCT/type: yes/0
Extra: 0166fd1ab355319b092d71c081cdbfef8782794eaf96513289626aad741d3b48f0021100000036b221b3d1000000000000000000

1 output(s) for total of 429.424305782000 dcy

stealth address amount amount idx
00: 906d0383ddfd25c1d19d1c0eb936f55ccfbf887878322d759302b1345f502ea6 429.424305782000 86295 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": 46824, "vin": [ { "gen": { "height": 46814 } } ], "vout": [ { "amount": 429424305782, "target": { "key": "906d0383ddfd25c1d19d1c0eb936f55ccfbf887878322d759302b1345f502ea6" } } ], "extra": [ 1, 102, 253, 26, 179, 85, 49, 155, 9, 45, 113, 192, 129, 205, 191, 239, 135, 130, 121, 78, 175, 150, 81, 50, 137, 98, 106, 173, 116, 29, 59, 72, 240, 2, 17, 0, 0, 0, 54, 178, 33, 179, 209, 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