Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 559c195b23aa5d1e1fbc4780be8b2c828c3d9019187869e7af9d815da035464e

Tx prefix hash: a96abbaa1a663ef95bde5ddbf2f5f7fd4144d7c11a74df4d22d0b26bf27621f9
Tx public key: b270cd8a3bd0e8a3d6817702567b45b593e663f7eebfa9df398691a3bb3e504d
Timestamp: 1710227097 Timestamp [UCT]: 2024-03-12 07:04:57 Age [y:d:h:m:s]: 01:010:05:08:00
Block: 976544 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 268279 RingCT/type: yes/0
Extra: 01b270cd8a3bd0e8a3d6817702567b45b593e663f7eebfa9df398691a3bb3e504d0211000000080011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2f76be014efe4f6e668e60adaefbe0c7e8e83b0bb26b6349ad560c5ffa6e260f 0.600000000000 1436539 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": 976554, "vin": [ { "gen": { "height": 976544 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2f76be014efe4f6e668e60adaefbe0c7e8e83b0bb26b6349ad560c5ffa6e260f" } } ], "extra": [ 1, 178, 112, 205, 138, 59, 208, 232, 163, 214, 129, 119, 2, 86, 123, 69, 181, 147, 230, 99, 247, 238, 191, 169, 223, 57, 134, 145, 163, 187, 62, 80, 77, 2, 17, 0, 0, 0, 8, 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