Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ffbb7365f9d669430442ddb2f20e5dbe3d029c6dfe39bd6503958ce08bf7354c

Tx prefix hash: 381d3dae578fe42c37bedb9a4d71c9bdfe29d982070e70d1be201b46b08be0b7
Tx public key: 505e55ab3e2954faf5f04c016e84ee2ae28b0bbcb0c7823a352426bb976a44e3
Timestamp: 1722519344 Timestamp [UCT]: 2024-08-01 13:35:44 Age [y:d:h:m:s]: 00:300:14:27:52
Block: 1078438 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 214790 RingCT/type: yes/0
Extra: 01505e55ab3e2954faf5f04c016e84ee2ae28b0bbcb0c7823a352426bb976a44e3021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4036bf92940cd65b01aad2aabc2594ee840cd7da213064482abeb8a1f184be97 0.600000000000 1551015 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": 1078448, "vin": [ { "gen": { "height": 1078438 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4036bf92940cd65b01aad2aabc2594ee840cd7da213064482abeb8a1f184be97" } } ], "extra": [ 1, 80, 94, 85, 171, 62, 41, 84, 250, 245, 240, 76, 1, 110, 132, 238, 42, 226, 139, 11, 188, 176, 199, 130, 58, 53, 36, 38, 187, 151, 106, 68, 227, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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