Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 56eb54ed5002d1d34037b054e078e25c6b3514cd4841d75c57278bd109ead7aa

Tx prefix hash: dfc2a25217280e323188d3128706f83456c68ba03a1f00792cb3f39e53e63ab8
Tx public key: 3b34eaf522e5044afdefffaf2ac65b632577994cd0681def1e47c5020bf7cb69
Timestamp: 1702201248 Timestamp [UCT]: 2023-12-10 09:40:48 Age [y:d:h:m:s]: 01:113:12:46:59
Block: 910003 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 342260 RingCT/type: yes/0
Extra: 013b34eaf522e5044afdefffaf2ac65b632577994cd0681def1e47c5020bf7cb690211000000074b8f5122000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0b41d26beb246edf8243114d71dfb1b30c8b24e5c42d6203e46b90e8d26dc9be 0.600000000000 1367142 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": 910013, "vin": [ { "gen": { "height": 910003 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0b41d26beb246edf8243114d71dfb1b30c8b24e5c42d6203e46b90e8d26dc9be" } } ], "extra": [ 1, 59, 52, 234, 245, 34, 229, 4, 74, 253, 239, 255, 175, 42, 198, 91, 99, 37, 119, 153, 76, 208, 104, 29, 239, 30, 71, 197, 2, 11, 247, 203, 105, 2, 17, 0, 0, 0, 7, 75, 143, 81, 34, 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