Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 898546df402decc47493c56c25077bf4c12fe6736663c318f40d2360e3779739

Tx prefix hash: 79bab986dbcb9d2119570df99c178f59493463af5331dca9b601d1122a74e5a3
Tx public key: 3f42decf3ab8f2f5ffa628e0c0527ed6d191b1b98258e0d0cc1300940fa1b7bc
Timestamp: 1728993864 Timestamp [UCT]: 2024-10-15 12:04:24 Age [y:d:h:m:s]: 00:099:14:32:26
Block: 1132123 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 71143 RingCT/type: yes/0
Extra: 013f42decf3ab8f2f5ffa628e0c0527ed6d191b1b98258e0d0cc1300940fa1b7bc021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 42614e12297dea3969b3844b087d3e09669c11c4e55e3dc4c6d38c12e0d46ec1 0.600000000000 1615036 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": 1132133, "vin": [ { "gen": { "height": 1132123 } } ], "vout": [ { "amount": 600000000, "target": { "key": "42614e12297dea3969b3844b087d3e09669c11c4e55e3dc4c6d38c12e0d46ec1" } } ], "extra": [ 1, 63, 66, 222, 207, 58, 184, 242, 245, 255, 166, 40, 224, 192, 82, 126, 214, 209, 145, 177, 185, 130, 88, 224, 208, 204, 19, 0, 148, 15, 161, 183, 188, 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