Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f8454a9533a939aaaf2dae2988c8b9b3dea09cd2d0e1c02e5b3db77abd7c9b2a

Tx prefix hash: 5cb8c898e075f8f08eef88acd7cb6420faa372725bf9f40ed9fa94bb1ddc78bd
Tx public key: 321ef71cb23844052eeda665f1e8b5030f26114bad0d88dbb23451257250dde4
Timestamp: 1641142683 Timestamp [UCT]: 2022-01-02 16:58:03 Age [y:d:h:m:s]: 03:006:05:28:26
Block: 408999 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 783458 RingCT/type: yes/0
Extra: 01321ef71cb23844052eeda665f1e8b5030f26114bad0d88dbb23451257250dde40211000000134a0f5013000000000000000000

1 output(s) for total of 27.091130453000 dcy

stealth address amount amount idx
00: 5bbaeb28d6e7da3d25eee6c2f0ccd9a6be04c8eaec2b6fb49020803c68e3409e 27.091130453000 811318 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": 409009, "vin": [ { "gen": { "height": 408999 } } ], "vout": [ { "amount": 27091130453, "target": { "key": "5bbaeb28d6e7da3d25eee6c2f0ccd9a6be04c8eaec2b6fb49020803c68e3409e" } } ], "extra": [ 1, 50, 30, 247, 28, 178, 56, 68, 5, 46, 237, 166, 101, 241, 232, 181, 3, 15, 38, 17, 75, 173, 13, 136, 219, 178, 52, 81, 37, 114, 80, 221, 228, 2, 17, 0, 0, 0, 19, 74, 15, 80, 19, 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