Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d0d7d326d6afd1a711cae89ed7bfc4faf1ac24a2c8df5ca8391fbdc67f3adb4d

Tx prefix hash: f63815a3875736ebd65075ebc97a03187b91058a714e4cf3ae4551515ef01d36
Tx public key: f1737b7296ebca65c42ff2c9895bf60bcc9829f8f689012be6349c0952dc60da
Timestamp: 1712927980 Timestamp [UCT]: 2024-04-12 13:19:40 Age [y:d:h:m:s]: 01:067:05:55:51
Block: 998906 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 308933 RingCT/type: yes/0
Extra: 01f1737b7296ebca65c42ff2c9895bf60bcc9829f8f689012be6349c0952dc60da02110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 822bb10fa5e40f9db8c96c48c2a433671e68872974b8613d1c7bdbb0fe6a907a 0.600000000000 1459380 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": 998916, "vin": [ { "gen": { "height": 998906 } } ], "vout": [ { "amount": 600000000, "target": { "key": "822bb10fa5e40f9db8c96c48c2a433671e68872974b8613d1c7bdbb0fe6a907a" } } ], "extra": [ 1, 241, 115, 123, 114, 150, 235, 202, 101, 196, 47, 242, 201, 137, 91, 246, 11, 204, 152, 41, 248, 246, 137, 1, 43, 230, 52, 156, 9, 82, 220, 96, 218, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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