Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a7dac011a6a631a420f04c365ed8ebf5e794d62bbe895ecbbf94056497a0f147

Tx prefix hash: 7ca8a0532542bdcb8887e44aa0c83c0a1885f91fa9f2946dc09843fd5b58bc1a
Tx public key: f1468f28de7408eb9d7904f0a3a00c0735148d78bb780526dcfd6ce9717b711a
Timestamp: 1716273575 Timestamp [UCT]: 2024-05-21 06:39:35 Age [y:d:h:m:s]: 01:029:05:38:07
Block: 1026673 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 281664 RingCT/type: yes/0
Extra: 01f1468f28de7408eb9d7904f0a3a00c0735148d78bb780526dcfd6ce9717b711a0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2d4794023c5ab0749e39621df157b7f10151614c7c6207df0e03ab3a37d83b0a 0.600000000000 1493882 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": 1026683, "vin": [ { "gen": { "height": 1026673 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2d4794023c5ab0749e39621df157b7f10151614c7c6207df0e03ab3a37d83b0a" } } ], "extra": [ 1, 241, 70, 143, 40, 222, 116, 8, 235, 157, 121, 4, 240, 163, 160, 12, 7, 53, 20, 141, 120, 187, 120, 5, 38, 220, 253, 108, 233, 113, 123, 113, 26, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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