Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7476be8f91c332fbd36891fa9f1365a343f7dddb7d76b3c86784f4a9a9919c9a

Tx prefix hash: 88ed588a64adb897b69313f5b12213bf2665d6b770f0f49472b178f90094c8e5
Tx public key: 4ffd4beb18dccb97f226253ef9745dc1f932280bc974443ee1f9adeb8f648566
Timestamp: 1580477413 Timestamp [UCT]: 2020-01-31 13:30:13 Age [y:d:h:m:s]: 05:133:20:35:37
Block: 55751 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1247629 RingCT/type: yes/0
Extra: 014ffd4beb18dccb97f226253ef9745dc1f932280bc974443ee1f9adeb8f648566021100000002bd0f9f9f000000000000000000

1 output(s) for total of 401.120278563000 dcy

stealth address amount amount idx
00: 1d1a9678276d2fbfe2ffe21bf508e061be218fe8746670958cf8f613bcaa7c36 401.120278563000 102874 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": 55761, "vin": [ { "gen": { "height": 55751 } } ], "vout": [ { "amount": 401120278563, "target": { "key": "1d1a9678276d2fbfe2ffe21bf508e061be218fe8746670958cf8f613bcaa7c36" } } ], "extra": [ 1, 79, 253, 75, 235, 24, 220, 203, 151, 242, 38, 37, 62, 249, 116, 93, 193, 249, 50, 40, 11, 201, 116, 68, 62, 225, 249, 173, 235, 143, 100, 133, 102, 2, 17, 0, 0, 0, 2, 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