Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 379ee6b09d5e870bedd433cf5be0ffb1e6b1d4374b0c8f0f3eb559f16a8b488b

Tx prefix hash: 967ca47cb145c667599316f5784e56b10d597639263000bbbecc52585b9c43ed
Tx public key: b80eb3d87b41f07680a9747752eb42ea6a562483143aac52e2c5a272ff0db26b
Timestamp: 1582110880 Timestamp [UCT]: 2020-02-19 11:14:40 Age [y:d:h:m:s]: 05:025:04:02:32
Block: 68096 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1171107 RingCT/type: yes/0
Extra: 01b80eb3d87b41f07680a9747752eb42ea6a562483143aac52e2c5a272ff0db26b0211000000194ac5aa02000000000000000000

1 output(s) for total of 365.065246118000 dcy

stealth address amount amount idx
00: 165bfef94eaa65b3963509394500a5e2181efd73ca74650e3264e6bae5eef7f6 365.065246118000 125472 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": 68106, "vin": [ { "gen": { "height": 68096 } } ], "vout": [ { "amount": 365065246118, "target": { "key": "165bfef94eaa65b3963509394500a5e2181efd73ca74650e3264e6bae5eef7f6" } } ], "extra": [ 1, 184, 14, 179, 216, 123, 65, 240, 118, 128, 169, 116, 119, 82, 235, 66, 234, 106, 86, 36, 131, 20, 58, 172, 82, 226, 197, 162, 114, 255, 13, 178, 107, 2, 17, 0, 0, 0, 25, 74, 197, 170, 2, 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