Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 38307a18c9c5386fc6a642ceeb6f8b739672b679863141e25697cfb8ee5b26fe

Tx prefix hash: f8462e74f49bfbc8231144e28397e850330b3d2ddf9c10adcc6841c788258217
Tx public key: f8a45a52fca3a7edcc226a43297258939bf0d860e3c06b8b28d1876965cf9692
Timestamp: 1579232609 Timestamp [UCT]: 2020-01-17 03:43:29 Age [y:d:h:m:s]: 04:346:02:34:38
Block: 47232 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1136881 RingCT/type: yes/0
Extra: 01f8a45a52fca3a7edcc226a43297258939bf0d860e3c06b8b28d1876965cf9692021100000003bd0f9f9f000000000000000000

1 output(s) for total of 428.057010503000 dcy

stealth address amount amount idx
00: 311543dc6a8081e4b5c87191f0e95640654e29501c5d12f3f8143d64cc9b8e96 428.057010503000 87276 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": 47242, "vin": [ { "gen": { "height": 47232 } } ], "vout": [ { "amount": 428057010503, "target": { "key": "311543dc6a8081e4b5c87191f0e95640654e29501c5d12f3f8143d64cc9b8e96" } } ], "extra": [ 1, 248, 164, 90, 82, 252, 163, 167, 237, 204, 34, 106, 67, 41, 114, 88, 147, 155, 240, 216, 96, 227, 192, 107, 139, 40, 209, 135, 105, 101, 207, 150, 146, 2, 17, 0, 0, 0, 3, 189, 15, 159, 159, 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