Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 651fef8f229d76facd74cd03347fe3d0d3541c6a272627fefb839933ff4a7016

Tx prefix hash: cc57ac57f6522a89b8a61fd56c33ac085c176d66fa2e6bdef97337b5cb85c7e0
Tx public key: 9dd99da5036685497ec40c10d3d0ab8e06dcbbb1527ff531309b90f52782922c
Timestamp: 1713550661 Timestamp [UCT]: 2024-04-19 18:17:41 Age [y:d:h:m:s]: 00:265:17:38:19
Block: 1004074 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 190222 RingCT/type: yes/0
Extra: 019dd99da5036685497ec40c10d3d0ab8e06dcbbb1527ff531309b90f52782922c02110000000b52d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 38515c2a93661f7063dc0fa7fd1cb75b3d5e74c4cf45d0ea39b426e9315f0a02 0.600000000000 1464640 of 15

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": 1004084, "vin": [ { "gen": { "height": 1004074 } } ], "vout": [ { "amount": 600000000, "target": { "key": "38515c2a93661f7063dc0fa7fd1cb75b3d5e74c4cf45d0ea39b426e9315f0a02" } } ], "extra": [ 1, 157, 217, 157, 165, 3, 102, 133, 73, 126, 196, 12, 16, 211, 208, 171, 142, 6, 220, 187, 177, 82, 127, 245, 49, 48, 155, 144, 245, 39, 130, 146, 44, 2, 17, 0, 0, 0, 11, 82, 212, 126, 148, 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