Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e08f550b9abab536e074e4dccb3adcc2d6cf2b080121c8e8b559a97b95687828

Tx prefix hash: c904b4dead7b29c8038862d1555f313eccc9b52c695ed288302c82fb916cd4e7
Tx public key: 47de738f6a0df66c41a1c33abddc61638cb16f349ac8ae2f6d6e3be1e96d1a8b
Timestamp: 1581950850 Timestamp [UCT]: 2020-02-17 14:47:30 Age [y:d:h:m:s]: 04:262:23:53:09
Block: 66920 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1080226 RingCT/type: yes/0
Extra: 0147de738f6a0df66c41a1c33abddc61638cb16f349ac8ae2f6d6e3be1e96d1a8b0211000000010aca7173000000000000000000

1 output(s) for total of 368.355423316000 dcy

stealth address amount amount idx
00: db0f7eb918ee1f506fceb96eff6bf33713e62813922e98e765a8bf50ee01a147 368.355423316000 123175 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": 66930, "vin": [ { "gen": { "height": 66920 } } ], "vout": [ { "amount": 368355423316, "target": { "key": "db0f7eb918ee1f506fceb96eff6bf33713e62813922e98e765a8bf50ee01a147" } } ], "extra": [ 1, 71, 222, 115, 143, 106, 13, 246, 108, 65, 161, 195, 58, 189, 220, 97, 99, 140, 177, 111, 52, 154, 200, 174, 47, 109, 110, 59, 225, 233, 109, 26, 139, 2, 17, 0, 0, 0, 1, 10, 202, 113, 115, 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