Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4204bcccc50e0a6dc870c8adcaa7e3d2069f1c7c28416cf6e70722a40a828fbf

Tx prefix hash: bfb663966baa897d5a68a7355e99e950d026a04696276fab78ed6f8c5971e929
Tx public key: b8a20d505b613c6b0dd62beea6e5a7e6f332ee4caf149f319d40c3ee0f793870
Timestamp: 1715222892 Timestamp [UCT]: 2024-05-09 02:48:12 Age [y:d:h:m:s]: 00:206:17:51:46
Block: 1017956 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 147992 RingCT/type: yes/0
Extra: 01b8a20d505b613c6b0dd62beea6e5a7e6f332ee4caf149f319d40c3ee0f7938700211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 209c6044aa4f8647df821133b9b99ccbd8c4caa86bf78b81a05eab1fafda7bf0 0.600000000000 1481741 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": 1017966, "vin": [ { "gen": { "height": 1017956 } } ], "vout": [ { "amount": 600000000, "target": { "key": "209c6044aa4f8647df821133b9b99ccbd8c4caa86bf78b81a05eab1fafda7bf0" } } ], "extra": [ 1, 184, 162, 13, 80, 91, 97, 60, 107, 13, 214, 43, 238, 166, 229, 167, 230, 243, 50, 238, 76, 175, 20, 159, 49, 157, 64, 195, 238, 15, 121, 56, 112, 2, 17, 0, 0, 0, 4, 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