Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c35c308136e0d901f0cd746eb537ed26b76965cf84bfe12e244906e483feec48

Tx prefix hash: bdcedbc793af8d7fd136d67a54eabdc0c744e85400b29c5ff43a5559fad86b48
Tx public key: d0ee4bf781312c31082adfbd10f86dfbd0fa0da88ce530d2ea4aaae6eae2d1e2
Timestamp: 1617569369 Timestamp [UCT]: 2021-04-04 20:49:29 Age [y:d:h:m:s]: 03:235:03:37:45
Block: 233278 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 927766 RingCT/type: yes/0
Extra: 01d0ee4bf781312c31082adfbd10f86dfbd0fa0da88ce530d2ea4aaae6eae2d1e2021100000028a1bbccc7000000000000000000

1 output(s) for total of 103.527022709000 dcy

stealth address amount amount idx
00: 0e5e36eba44d5676d9ec7f5fe3d9da400c74d8c13b540561b9316dfbe231b2d2 103.527022709000 484494 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": 233288, "vin": [ { "gen": { "height": 233278 } } ], "vout": [ { "amount": 103527022709, "target": { "key": "0e5e36eba44d5676d9ec7f5fe3d9da400c74d8c13b540561b9316dfbe231b2d2" } } ], "extra": [ 1, 208, 238, 75, 247, 129, 49, 44, 49, 8, 42, 223, 189, 16, 248, 109, 251, 208, 250, 13, 168, 140, 229, 48, 210, 234, 74, 170, 230, 234, 226, 209, 226, 2, 17, 0, 0, 0, 40, 161, 187, 204, 199, 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