Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1fab8a395532fd73b8834a6db35a95968a2b4109350025a27d3474bc18f87878

Tx prefix hash: 2736f7acf8d7f59753b9a01f190064a77c4cad57d0cbf0f7d3b81ebf247614e3
Tx public key: 54e9557bd1e745488fcda71412f5e192b30772f250e9ed57ae1aa1d027a5f848
Timestamp: 1719813659 Timestamp [UCT]: 2024-07-01 06:00:59 Age [y:d:h:m:s]: 00:205:12:08:48
Block: 1056008 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 147012 RingCT/type: yes/0
Extra: 0154e9557bd1e745488fcda71412f5e192b30772f250e9ed57ae1aa1d027a5f84802110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0b50d6469f2a1e671313682f340f69d8c783e3de8b18be6c862a58264d9482f8 0.600000000000 1526419 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": 1056018, "vin": [ { "gen": { "height": 1056008 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0b50d6469f2a1e671313682f340f69d8c783e3de8b18be6c862a58264d9482f8" } } ], "extra": [ 1, 84, 233, 85, 123, 209, 231, 69, 72, 143, 205, 167, 20, 18, 245, 225, 146, 179, 7, 114, 242, 80, 233, 237, 87, 174, 26, 161, 208, 39, 165, 248, 72, 2, 17, 0, 0, 0, 1, 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