Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c78b890f80519ee363577b259557391c6186fac8d4c4a558a5a30754ff63a0c9

Tx prefix hash: fc2c1b6c01bdfa2a6e345613841b65872b6588c1cac087d5a1833ad2832dc93c
Tx public key: 3d0a5eab0eedb2ad1ce9878564ac6180471de11306336e353d13f19593a3a90c
Timestamp: 1581948721 Timestamp [UCT]: 2020-02-17 14:12:01 Age [y:d:h:m:s]: 05:107:07:44:11
Block: 66813 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1229805 RingCT/type: yes/0
Extra: 013d0a5eab0eedb2ad1ce9878564ac6180471de11306336e353d13f19593a3a90c02110000000203d36d11000000000000000000

1 output(s) for total of 368.656252425000 dcy

stealth address amount amount idx
00: dc76a22c628d6a53edc127a1090baa3dcbb0a9613b92079e142694b895b58cd3 368.656252425000 123021 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": 66823, "vin": [ { "gen": { "height": 66813 } } ], "vout": [ { "amount": 368656252425, "target": { "key": "dc76a22c628d6a53edc127a1090baa3dcbb0a9613b92079e142694b895b58cd3" } } ], "extra": [ 1, 61, 10, 94, 171, 14, 237, 178, 173, 28, 233, 135, 133, 100, 172, 97, 128, 71, 29, 225, 19, 6, 51, 110, 53, 61, 19, 241, 149, 147, 163, 169, 12, 2, 17, 0, 0, 0, 2, 3, 211, 109, 17, 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