Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b994d13f9d76ae3e5e643a9b843516dd8935e5793b06b711ea2f978ced268107

Tx prefix hash: 008c2a9db5951b4087edfb638ae3ea304c8bbecb9e8cbba8a24b2781c1d9cc29
Tx public key: 053ba6508d02283af4efeb33c6e58487d61f8188bd7be1d98d9d62109e41f4dd
Timestamp: 1726962500 Timestamp [UCT]: 2024-09-21 23:48:20 Age [y:d:h:m:s]: 00:220:02:07:13
Block: 1115280 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 157135 RingCT/type: yes/0
Extra: 01053ba6508d02283af4efeb33c6e58487d61f8188bd7be1d98d9d62109e41f4dd02110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0cc13c1540a40c28afade288d9e37467b06fbf984bcf99a90a115a2bd0ae3238 0.600000000000 1595359 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": 1115290, "vin": [ { "gen": { "height": 1115280 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0cc13c1540a40c28afade288d9e37467b06fbf984bcf99a90a115a2bd0ae3238" } } ], "extra": [ 1, 5, 59, 166, 80, 141, 2, 40, 58, 244, 239, 235, 51, 198, 229, 132, 135, 214, 31, 129, 136, 189, 123, 225, 217, 141, 157, 98, 16, 158, 65, 244, 221, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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