Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fff26f307f9c81644c05b2b356fa2be7b0e2759f0306f6573f96106f089cb776

Tx prefix hash: f652a6c0f6ffdf3ce8c897ef25f21d306074f5e7adf9af10b56f2ef5559daba6
Tx public key: e7d3229bb1d87c50aeb51da6a08786b6ce454484ef2f9a9d6c12e7e92233dacb
Timestamp: 1706475767 Timestamp [UCT]: 2024-01-28 21:02:47 Age [y:d:h:m:s]: 01:080:08:07:52
Block: 945411 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 318508 RingCT/type: yes/0
Extra: 01e7d3229bb1d87c50aeb51da6a08786b6ce454484ef2f9a9d6c12e7e92233dacb0211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e59656c986f8e38b3af4c1b49881403987b35860eb8862c943580bd08eef8257 0.600000000000 1403725 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": 945421, "vin": [ { "gen": { "height": 945411 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e59656c986f8e38b3af4c1b49881403987b35860eb8862c943580bd08eef8257" } } ], "extra": [ 1, 231, 211, 34, 155, 177, 216, 124, 80, 174, 181, 29, 166, 160, 135, 134, 182, 206, 69, 68, 132, 239, 47, 154, 157, 108, 18, 231, 233, 34, 51, 218, 203, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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