Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2cc775c9875abbeddb6d5fbb98add8eebffda9a3e06da4095149019089182460

Tx prefix hash: 38c8e34a997d0cc200b3c3f8f323d0ba204ab4a3c2026d0ce7043a93f309d521
Tx public key: 027ce8830455b34d0f8ac7d4ebacdecfb32db7be1d7fb23cfbc0c4d7e8939c9e
Timestamp: 1614043379 Timestamp [UCT]: 2021-02-23 01:22:59 Age [y:d:h:m:s]: 03:304:06:19:35
Block: 204642 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 976685 RingCT/type: yes/0
Extra: 01027ce8830455b34d0f8ac7d4ebacdecfb32db7be1d7fb23cfbc0c4d7e8939c9e0211000000664ea414e5000000000000000000

1 output(s) for total of 128.806185587000 dcy

stealth address amount amount idx
00: 1c6e11d07d9ed47f59b1d6067ba3fbe13681fae58d885b9f7c268e60a6eabf35 128.806185587000 418212 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": 204652, "vin": [ { "gen": { "height": 204642 } } ], "vout": [ { "amount": 128806185587, "target": { "key": "1c6e11d07d9ed47f59b1d6067ba3fbe13681fae58d885b9f7c268e60a6eabf35" } } ], "extra": [ 1, 2, 124, 232, 131, 4, 85, 179, 77, 15, 138, 199, 212, 235, 172, 222, 207, 179, 45, 183, 190, 29, 127, 178, 60, 251, 192, 196, 215, 232, 147, 156, 158, 2, 17, 0, 0, 0, 102, 78, 164, 20, 229, 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