Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0faa59125c529707a0f2ef8e9053dc7ee7360db4e6ca7e1ccd96f61426b2ba0c

Tx prefix hash: 251dbf9cfc2cd4a3acd6753e70dd94ece56e9efa25427bd3a878c521c5ed4d44
Tx public key: b51eb770d520b4fefc7fab36ff2956f2210fd84359d9f4288acfdf00d9ddb6bd
Timestamp: 1722182714 Timestamp [UCT]: 2024-07-28 16:05:14 Age [y:d:h:m:s]: 00:253:15:09:13
Block: 1075651 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 181166 RingCT/type: yes/0
Extra: 01b51eb770d520b4fefc7fab36ff2956f2210fd84359d9f4288acfdf00d9ddb6bd021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 58decf6334e37d247450260a8d5e3575f4d96b4616a5fdfcd08359a0d5677ed1 0.600000000000 1548180 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": 1075661, "vin": [ { "gen": { "height": 1075651 } } ], "vout": [ { "amount": 600000000, "target": { "key": "58decf6334e37d247450260a8d5e3575f4d96b4616a5fdfcd08359a0d5677ed1" } } ], "extra": [ 1, 181, 30, 183, 112, 213, 32, 180, 254, 252, 127, 171, 54, 255, 41, 86, 242, 33, 15, 216, 67, 89, 217, 244, 40, 138, 207, 223, 0, 217, 221, 182, 189, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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