Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 45698162fa6d7057978cc8bce4a3cc00e18ff2c997972facf319a75b7d5da911

Tx prefix hash: 6aa27ed605eed8132cbf0f40b32bb19b8a2e69b72c813c9bf2719068d68dff2f
Tx public key: baad36c2bfac983ce1a4f7a69876715a427ec0c8f6dbc45fa2248752ecd3df8b
Timestamp: 1657024461 Timestamp [UCT]: 2022-07-05 12:34:21 Age [y:d:h:m:s]: 03:118:14:11:14
Block: 537172 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 864467 RingCT/type: yes/0
Extra: 01baad36c2bfac983ce1a4f7a69876715a427ec0c8f6dbc45fa2248752ecd3df8b02110000000ba8c141c5000000000000000000

1 output(s) for total of 10.188877115000 dcy

stealth address amount amount idx
00: 088582e0965eb337ad9e0fa3bd6688526e3a84e275dc27aafcf5c87d611a2402 10.188877115000 967031 of 0

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": 537182, "vin": [ { "gen": { "height": 537172 } } ], "vout": [ { "amount": 10188877115, "target": { "key": "088582e0965eb337ad9e0fa3bd6688526e3a84e275dc27aafcf5c87d611a2402" } } ], "extra": [ 1, 186, 173, 54, 194, 191, 172, 152, 60, 225, 164, 247, 166, 152, 118, 113, 90, 66, 126, 192, 200, 246, 219, 196, 95, 162, 36, 135, 82, 236, 211, 223, 139, 2, 17, 0, 0, 0, 11, 168, 193, 65, 197, 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