Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1c0d3a62de0ab5e4cd912e0c3bb7c4969b59079427f0f83b3298c5b576bb42cc

Tx prefix hash: 2b12d7598ea80b25a72f7a170a608f7ee22a767f01eb14e81e5c973b897cb408
Tx public key: 0c71f84800ee81c9dc712cb50bd97a27c2c439647bfab2bf6dbe15b7bf8313a0
Timestamp: 1636988850 Timestamp [UCT]: 2021-11-15 15:07:30 Age [y:d:h:m:s]: 03:054:05:23:24
Block: 374885 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 817520 RingCT/type: yes/0
Extra: 010c71f84800ee81c9dc712cb50bd97a27c2c439647bfab2bf6dbe15b7bf8313a0021100000005a272b9cb000000000000000000

1 output(s) for total of 35.145545180000 dcy

stealth address amount amount idx
00: ec6dbe06a93194d4dfa1d253dbb9486b51be8d93153a955283fae265bf58d5f5 35.145545180000 758701 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": 374895, "vin": [ { "gen": { "height": 374885 } } ], "vout": [ { "amount": 35145545180, "target": { "key": "ec6dbe06a93194d4dfa1d253dbb9486b51be8d93153a955283fae265bf58d5f5" } } ], "extra": [ 1, 12, 113, 248, 72, 0, 238, 129, 201, 220, 113, 44, 181, 11, 217, 122, 39, 194, 196, 57, 100, 123, 250, 178, 191, 109, 190, 21, 183, 191, 131, 19, 160, 2, 17, 0, 0, 0, 5, 162, 114, 185, 203, 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