Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: db50c5210ee8d1dc57a090dc63f3b1ce3ef1016a1cd6d0bfa96a5852398e4ffe

Tx prefix hash: de3139aa82aa8fce6a6e851bb37b51edf6c967eac2887ced8288388d8219ca0b
Tx public key: 21dc1e7d16cfe8bc1383e9f80f3406d4f87fb693f5c848aea266e178c125600c
Timestamp: 1598186447 Timestamp [UCT]: 2020-08-23 12:40:47 Age [y:d:h:m:s]: 04:138:09:32:29
Block: 128993 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1063460 RingCT/type: yes/0
Extra: 0121dc1e7d16cfe8bc1383e9f80f3406d4f87fb693f5c848aea266e178c125600c021100000124362de607000000000000000000

1 output(s) for total of 229.399973646000 dcy

stealth address amount amount idx
00: 5cc917680eec7a9757205a7117d514047d322f02b1050db062c79ec5251215dc 229.399973646000 216507 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": 129003, "vin": [ { "gen": { "height": 128993 } } ], "vout": [ { "amount": 229399973646, "target": { "key": "5cc917680eec7a9757205a7117d514047d322f02b1050db062c79ec5251215dc" } } ], "extra": [ 1, 33, 220, 30, 125, 22, 207, 232, 188, 19, 131, 233, 248, 15, 52, 6, 212, 248, 127, 182, 147, 245, 200, 72, 174, 162, 102, 225, 120, 193, 37, 96, 12, 2, 17, 0, 0, 1, 36, 54, 45, 230, 7, 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