Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2716b50b4f81aab11546e970b38e0c1b877d4a2aacef9ac2f6201c0fa65d913b

Tx prefix hash: 2b38342affd45641c5fa4914ea4581a06432ce4419dffb94879fbce82197947e
Tx public key: 268039b0e3e5417c4f7026a60eac4539600892fbed3f59b5cfaadae829fb99e2
Timestamp: 1636150797 Timestamp [UCT]: 2021-11-05 22:19:57 Age [y:d:h:m:s]: 03:190:11:02:01
Block: 368137 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 914514 RingCT/type: yes/0
Extra: 01268039b0e3e5417c4f7026a60eac4539600892fbed3f59b5cfaadae829fb99e20211000000016e80e2c6000000000000000000

1 output(s) for total of 37.001319102000 dcy

stealth address amount amount idx
00: 0edca9116c8f50811b67d73ac15b359b9b310e396ae6a4012a136fba15256c02 37.001319102000 746779 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": 368147, "vin": [ { "gen": { "height": 368137 } } ], "vout": [ { "amount": 37001319102, "target": { "key": "0edca9116c8f50811b67d73ac15b359b9b310e396ae6a4012a136fba15256c02" } } ], "extra": [ 1, 38, 128, 57, 176, 227, 229, 65, 124, 79, 112, 38, 166, 14, 172, 69, 57, 96, 8, 146, 251, 237, 63, 89, 181, 207, 170, 218, 232, 41, 251, 153, 226, 2, 17, 0, 0, 0, 1, 110, 128, 226, 198, 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