Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 942d4439bcb54a563a8c372c2e18a3bf8c5dced0873c1bd3ed43748ab60b80d8

Tx prefix hash: a12a3e5529ffec823aac164e93e66108f2416d78ef1b5117a75db0cb4e83aaf8
Tx public key: fcbd6c779da30a7322030ee56d293dac5ca1120aed3a8d2e3103ab74b6d48ac0
Timestamp: 1735803015 Timestamp [UCT]: 2025-01-02 07:30:15 Age [y:d:h:m:s]: 00:353:03:18:04
Block: 1188442 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 249945 RingCT/type: yes/0
Extra: 01fcbd6c779da30a7322030ee56d293dac5ca1120aed3a8d2e3103ab74b6d48ac0021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fd747721c99800ff4ec9544474918d3d6cef835c3f1b66f7a1763c88ecd40e2c 0.600000000000 1674943 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": 1188452, "vin": [ { "gen": { "height": 1188442 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fd747721c99800ff4ec9544474918d3d6cef835c3f1b66f7a1763c88ecd40e2c" } } ], "extra": [ 1, 252, 189, 108, 119, 157, 163, 10, 115, 34, 3, 14, 229, 109, 41, 61, 172, 92, 161, 18, 10, 237, 58, 141, 46, 49, 3, 171, 116, 182, 212, 138, 192, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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