Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 06ce0bbfa8be2097f3cefd3f3b0796e5c935343321d2af9f93d2b73a2ccc9b3e

Tx prefix hash: 849f81d3792e1130d3d9653e432a27cd25897f95fe2e0531144208d85d9a8e19
Tx public key: da33a743d2e08be77311be52a6da834d46b33da99a9a69ff1305efbba0a77c52
Timestamp: 1713928020 Timestamp [UCT]: 2024-04-24 03:07:00 Age [y:d:h:m:s]: 00:345:15:49:02
Block: 1007217 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 247096 RingCT/type: yes/0
Extra: 01da33a743d2e08be77311be52a6da834d46b33da99a9a69ff1305efbba0a77c5202110000000141ee1c9b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7e7530af94444a06dba6db6d6ebb9ccef6a273f14963e69f3577e41a0cf342a5 0.600000000000 1468485 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": 1007227, "vin": [ { "gen": { "height": 1007217 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7e7530af94444a06dba6db6d6ebb9ccef6a273f14963e69f3577e41a0cf342a5" } } ], "extra": [ 1, 218, 51, 167, 67, 210, 224, 139, 231, 115, 17, 190, 82, 166, 218, 131, 77, 70, 179, 61, 169, 154, 154, 105, 255, 19, 5, 239, 187, 160, 167, 124, 82, 2, 17, 0, 0, 0, 1, 65, 238, 28, 155, 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