Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b6b94d3ebdbda955d89307da2fbcb2c0fca3d7aa864812c1a1dc2d870850c7b3

Tx prefix hash: 3ae4a986a0d51bd75f7e1092dac93c8472e8133e25e98b4e84435c6fbe44c902
Tx public key: fc63145306b99e3504f80381d51f4fb666fe7d606da1afc781062983fcaaf542
Timestamp: 1689103730 Timestamp [UCT]: 2023-07-11 19:28:50 Age [y:d:h:m:s]: 01:270:17:42:21
Block: 801674 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 454606 RingCT/type: yes/0
Extra: 01fc63145306b99e3504f80381d51f4fb666fe7d606da1afc781062983fcaaf542021100000005e6d27f9c000000000000000000

1 output(s) for total of 1.354320258000 dcy

stealth address amount amount idx
00: 898c6704f30c91d1562964b279a7cd1ad724e3533fe503ea35f9f333279f04b9 1.354320258000 1252771 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": 801684, "vin": [ { "gen": { "height": 801674 } } ], "vout": [ { "amount": 1354320258, "target": { "key": "898c6704f30c91d1562964b279a7cd1ad724e3533fe503ea35f9f333279f04b9" } } ], "extra": [ 1, 252, 99, 20, 83, 6, 185, 158, 53, 4, 248, 3, 129, 213, 31, 79, 182, 102, 254, 125, 96, 109, 161, 175, 199, 129, 6, 41, 131, 252, 170, 245, 66, 2, 17, 0, 0, 0, 5, 230, 210, 127, 156, 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